1
00:00:13,290 --> 00:00:18,310
So let us continue with our top 10 attacks in the last lecture.

2
00:00:18,570 --> 00:00:22,840
These are the first five top 10 attacks and I'm in this lecture.

3
00:00:23,190 --> 00:00:25,380
We will explore the remaining attacks.

4
00:00:27,000 --> 00:00:35,670
ASX security misconfiguration using misconfiguration vulnerabilities like unvalidated inputs, parameter

5
00:00:35,670 --> 00:00:43,080
tampering, improper error handling, insufficient transport, layer protection, etc., attackers gain

6
00:00:43,080 --> 00:00:50,160
unauthorized access to default accounts, unused pages, retrade unprotected files and directories and

7
00:00:50,160 --> 00:00:51,810
minimum security.

8
00:00:51,810 --> 00:00:59,250
Misconfiguration can occur at any level of application stack, including the platform web server application

9
00:00:59,250 --> 00:01:04,590
server framework and custom cool water unvalidated inputs.

10
00:01:05,020 --> 00:01:12,510
It refers to Web application vulnerability, where input from a client is not validated before being

11
00:01:12,510 --> 00:01:15,750
processed by other applications and back in.

12
00:01:15,780 --> 00:01:18,390
So what is parameter tampering?

13
00:01:18,990 --> 00:01:26,810
It involves manipulation of parameters like price tags or sessions exchanged between client and server

14
00:01:26,820 --> 00:01:29,060
in order to modify application data.

15
00:01:29,910 --> 00:01:31,380
Improper error handling.

16
00:01:31,890 --> 00:01:39,060
It gives insight into source code such as logic flaws, default accounts, etc. and using the information

17
00:01:39,060 --> 00:01:45,360
received from error message, attacker can identify vulnerabilities for launching various application

18
00:01:45,360 --> 00:01:45,870
attacks.

19
00:01:46,860 --> 00:01:51,390
The next is a seven that is cross site scripting attack.

20
00:01:52,590 --> 00:01:57,520
You have heard of the storm in many different hacking forums or blogs.

21
00:01:57,750 --> 00:02:01,260
So what is Exercice Cross site scripting?

22
00:02:01,290 --> 00:02:08,670
That is Exercice Odysseas attacks exploit vulnerabilities in dynamically generated Web pages, which

23
00:02:08,670 --> 00:02:15,910
enables malicious attackers to inject Clydeside script into Web pages viewed by other users.

24
00:02:16,350 --> 00:02:22,560
So if you are an attacker, you will inject a malicious code into that web browser or the application.

25
00:02:22,860 --> 00:02:29,550
And whenever a legitimate user will open that web application, he can see your executed error message.

26
00:02:30,480 --> 00:02:37,770
No exercice occurs when invalidated input data is included in a dynamic content that is sent to the

27
00:02:37,770 --> 00:02:47,940
user's web browser for rendering attackers in malicious JavaScript VB Script ActiveX HTML or flash for

28
00:02:47,940 --> 00:02:52,710
execution on a victim system by hiding it within legitimate requests.

29
00:02:53,790 --> 00:03:00,510
Some of the excesses attack exploitation include malicious script execution, redirecting to malicious

30
00:03:00,510 --> 00:03:07,920
server exploiting user privileges now adds a hidden Ephraim's and pop ups are also exercice attacks.

31
00:03:08,530 --> 00:03:13,290
We will explode Xerces attacks and practicals in this section.

32
00:03:13,980 --> 00:03:15,840
Where can you see Exercice attacks?

33
00:03:16,110 --> 00:03:24,660
Well, you can see an exercise attack in e-mails, in blogs, in command fields and websites which are

34
00:03:24,660 --> 00:03:27,090
vulnerable to attacks and other things.

35
00:03:28,200 --> 00:03:30,270
It insecure.

36
00:03:30,480 --> 00:03:39,270
The serialisation, data, serialisation and database utilization is an effective process of línea raising

37
00:03:39,270 --> 00:03:47,340
and dealing, erasing data objects in order to transport it to other network assistance attackers in

38
00:03:47,520 --> 00:03:53,100
malicious code and to serialize data and follow the malicious serialized data to the victim.

39
00:03:54,240 --> 00:04:01,080
Insecurities, utilization, because realizes the malicious serialized content along with the injected

40
00:04:01,080 --> 00:04:09,600
malicious code, compromising the system or network, the last on the second act is using components

41
00:04:09,750 --> 00:04:15,900
with no known relatives, no components such as libraries and frameworks that are used in most of the

42
00:04:15,900 --> 00:04:23,310
Web applications always execute with full privileges and flaws in any component can result in serious

43
00:04:23,490 --> 00:04:24,180
impact.

44
00:04:24,780 --> 00:04:30,970
Attackers can identify components or dependencies by scanning or performing manual analysis.

45
00:04:31,800 --> 00:04:38,100
For example, if you are developing an app and you want to insert a payment gateway to your app, you

46
00:04:38,100 --> 00:04:42,770
will not write an entire code to develop a payment gateway by yourself.

47
00:04:42,780 --> 00:04:48,630
You will hire or they will just get a plug in for a third party payment gateway and then include it

48
00:04:48,630 --> 00:04:49,210
in your code.

49
00:04:49,740 --> 00:04:56,130
But what if that third party payment gateway has already exploited Audobon the dignity that is known

50
00:04:56,130 --> 00:05:04,410
as using components with nonlinearities and the last of the up stopped and vulnerabilities is insufficient.

51
00:05:04,410 --> 00:05:11,670
Logging and monitoring web applications maintain logs to track usage patterns such as user login credentials

52
00:05:11,670 --> 00:05:13,410
and admin login credentials.

53
00:05:14,190 --> 00:05:20,340
Insufficient logging and monitoring refers to the scenario whether detection software either does not

54
00:05:20,340 --> 00:05:25,380
record the malicious event or ignores the important details about the event.

55
00:05:26,490 --> 00:05:34,710
Attackers usually inject, delete, tamper with applications to engage in malicious activities or hide

56
00:05:34,710 --> 00:05:41,490
their identities, insufficient logging and monitoring when that really makes the detection of malicious

57
00:05:41,490 --> 00:05:47,760
attempts of the attacker more difficult and allowing the attacker to perform malicious attacks like

58
00:05:47,760 --> 00:05:51,510
brute forcing passwords to steal confidential passwords.

59
00:05:52,950 --> 00:05:56,420
Now, these are the Web's top 10 vulnerabilities.

60
00:05:56,670 --> 00:06:00,650
But that doesn't mean that these are the only vulnerabilities present.

61
00:06:01,230 --> 00:06:08,700
Other vulnerabilities like directly traversal denial-of-service, hidden field manipulation, platform

62
00:06:08,700 --> 00:06:17,400
exploits, cross site request forgery, waterhole attacks, broken session management, network access

63
00:06:17,400 --> 00:06:24,520
attacks, kookie snooping and many more, you name it, and you get a vulnerability for that attack.

64
00:06:25,080 --> 00:06:31,530
So basically, these are the most common attacks and therefore they are being listed as the top 10 attacks

65
00:06:31,530 --> 00:06:37,530
by all APS or APS is open source free organization, which provides bank testing methodologies.

66
00:06:37,890 --> 00:06:44,610
Then it also provides tutorials, various books and a framework to carry out a proper web application

67
00:06:44,730 --> 00:06:45,860
penetration testing.

68
00:06:46,470 --> 00:06:53,430
So in the next lecture, we will see how to footprint a website using different tools, such as who

69
00:06:53,430 --> 00:06:56,520
is built with current employees and others.

70
00:06:56,970 --> 00:07:03,810
So in short, from the next lecture will be starting the application penetration testing practicals.
